Skip to main content
TrustRadius
Ansible

Ansible

Overview

What is Ansible?

The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments…

Read more
Recent Reviews
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons

Video Reviews

3 videos

Is it worth it? | Red Hat Ansible Automation Platform Review
04:14
Red Hat Ansible Automation Platform Review | Words from an Automation Architect
03:12
Red Hat Ansible Automation Platform Review | Systems Admin Thoughts
06:37
Return to navigation

Pricing

View all pricing

Basic Tower

5,000

On Premise
per year

Enterprise Tower

10,000

On Premise
per year

Premium Tower

14,000

On Premise
per year

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Demos

WebLogic Continuous Deployment with Red Hat Ansible Automation Platform

YouTube

Trusted Automation Series: F5 BigIP

YouTube

Manage your Cisco devices with Red Hat Ansible Automation Platform

YouTube

Network Automation Basics - First Ansible Playbook

YouTube

Deep Dive - Automated NetOps - Ansible for Network GitOps

YouTube
Return to navigation

Product Details

What is Ansible?

The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.

Its Automation Hub provides a one-stop-shop for Ansible content that is backed by support from Red Hat and its partners to deliver additional reassurance for demanding environments.

The Ansible project and Ansible Engine are open source technologies. The Ansible project is built by the community (ansible.com/community) for the benefit of the community. Ansible Engine is developed by Red Hat with the explicit intent of being used as an enterprise IT platform.

Ansible Technical Details

Deployment TypesOn-premise
Operating SystemsLinux
Mobile ApplicationNo

Frequently Asked Questions

The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.

Reviewers rate Performance highest, with a score of 8.7.

The most common users of Ansible are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(258)

Attribute Ratings

Reviews

(1-3 of 3)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
Incentivized
The platform addresses several business problems, such as:

1.) Manual and repetitive tasks: Ansible Automation Platform helps eliminate manual, repetitive tasks by automating them. This reduces human error, increases efficiency, and allows IT teams to focus on more strategic initiatives.

2.) Configuration management: Managing configurations across a large number of systems can be challenging. Ansible Automation Platform enables centralized management of configurations, ensuring consistency and compliance across the infrastructure.

3.) Application deployment and orchestration: Deploying and managing applications across different environments can be time-consuming and error-prone. Ansible Automation Platform simplifies application deployment and provides orchestration capabilities to streamline the process.

4.) Infrastructure provisioning: Provisioning and managing infrastructure resources can be complex, especially in cloud or hybrid environments. Ansible Automation Platform helps automate infrastructure provisioning, enabling organizations to scale resources efficiently and consistently.
  • Configuration management at scale
  • Infrastructure as code
  • Cross-platform and cross-environment compatibility
  • Managing systems off corporate network; i.e. company provided equipment.
  • Think windows MDM... how do we manage systems off of corporate network.
Based on its idempotent nature, Red Hat Ansible Automation Platform is well suited for the following scenarios:

1.) Configuration management: Ansible excels in managing and maintaining consistent configurations across a large number of systems. Whether it's configuring software, network devices, or infrastructure components, Ansible's idempotent operations ensure that desired states are achieved and maintained, even in complex environments.

2.) Continuous deployment and integration (CI/CD): Ansible is well suited for automating application deployment and orchestrating CI/CD pipelines. Its idempotent execution ensures consistent and reproducible deployments, making it easier to roll out updates, manage multiple environments, and integrate with popular CI/CD tools.

3.) Infrastructure provisioning and orchestration: Ansible is an excellent choice for provisioning and managing infrastructure resources. Its idempotent playbooks enable organizations to automate the creation and configuration of servers, virtual machines, containers, and cloud resources, allowing for scalable and consistent infrastructure provisioning.

4.) System administration and operations: Ansible's idempotent nature makes it ideal for system administration tasks and operational automation. Whether it's managing user accounts, updating software packages, or performing routine maintenance tasks, Ansible ensures that operations are executed reliably and consistently across different systems and environments.

Ansible is the way...
  • Community and ecosystem behind Ansible
  • An extensive list of modules to get things done
  • Increased efficiency and productivity: By automating manual and repetitive tasks, organizations can achieve significant time savings and improve overall operational efficiency.
  • Consistency and compliance: Ansible Automation Platform helps enforce consistent configurations and policy compliance across the infrastructure.
December 01, 2017

DevOps Swiss Army Knife

Aiman Najjar | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Ansible is a powerful tool for many DevOps cases, including generic automation scripts, configuration management, and infrastructure orchestration. We've used it mainly for complex application deployments - for each application, we wrote an Ansible playbook to deploy the application and all dependencies to target Chef-managed environments. The deployment process for each application varied a lot and was often very complex, and each playbook would have different logic for configuration and validations.

Those applications ranged from J2EE applications to cron jobs. Target VMs would range from Tomcat application servers to plain Linux machines.

I have also used Ansible for other uses such as for simplifying interaction with a large cluster of nodes to perform system administration tasks (e.g. fetching logs, investigating issues across nodes of a cluster..etc). I have also used its Python library to create custom automation scripts. It worked very well for all cases above.
  • Decentralized configuration management - Ansible supports "desired state" syntax and is a great alternative to centralized configuration management solutions. If you think that maintaining an infrastructure is an overkill for your needs, then you should consider Ansible. Ansible is "agentless" and all you need is version control, SSH access, and proper organization skills!
  • Great for writing clean and readable automation scripts. In my opinion, Ansible Playbooks are the new Shell scripts. It enforces readable structure yet maintains a great flexibility. Add to that, the ability to write playbooks in reusable "roles" as well as the large repository of built-in Ansible modules, Ansible becomes a very awesome alternative to writing complex Shell/Bash scripts.
  • Very powerful tool for system administrators to reliably and quickly interact with nodes of large clusters. With proper organization of your host inventory in versioned-control files, Ansible becomes an indispensable tool for Sys Admins to investigate issues and perform routine tasks across large clusters.
  • Steep learning curve - I have found that Ansible has a steeper learning curve when it comes to playbooks and roles. This could be a side-effect of its power and flexibility. I still believe more could be done to make writing roles simpler.
  • There is no a public repository of playbooks or a "package manager" that facilitates download community-maintained Ansible playbooks.
Ansible is really unique in that it works well for various DevOps needs. I find it very well suited for:
  1. Automation Scripts - think: deployment scripts, configuration scripts, start-up/shut-down scripts, cron jobs, etc.
  2. Infrastructure as Code - although I would not say it is Ansible's primary use case, Ansible still has a good amount (albeit not comprehensive) of cloud infrastructure orchestration modules, things like creating EC2 instances, ELBs, S3 buckets, Azure resources, etc.
  3. Decentralized / "Push" Configuration Management - that means you trigger Ansible from a client machine and it will remotely execute the configuration scripts over SSH. This is actually enough for many configuration management use cases.

It may not work extremely well for the following cases:

  1. Complex Infrastructure as Code needs - i.e. cloud infrastructure that consists of many cloud resources of different types and advanced configuration.
  2. Configuring Complex Clusters or Ecosystems - for this I would prefer "Pull" / Centralized Configuration Management solution that offers inventory look-ups and integrated data store solution as part of the configuration process.
  • Ansible is a great investment if used for its well-suited scenarios. It has had a positive impact on my clients who used it to modernize their application deployment process. Ansible has 1) increased the reliability of the deployment process and 2) reduced scripts maintenance overhead.
  • Since Ansible is simpler and faster to get started with - compared to centralized configuration management solutions - it can be tempting to use it initially for simpler applications/infrastructure that are anticipated to evolve to complex ecosystems, you may find yourself having to rewrite in another tool in such cases.
  • Ansible is much simpler to get up and running with than Chef, as it requires no infrastructure or agent process or any configuration on the target machine. All you need is SSH access! However, you lose the capabilities that Chef server offers such as data bags (centralized data store with support for encryption), authorization rules, inventory status, periodic configuration pulls, version locking etc.
  • Ansible combines both infrastructure orchestration and configuration capabilities, therefore it can be used as a single tool to both create and configure your VMs on the cloud. However, it lacks the comprehensive support of various cloud resource types that Terraform offers. Terraform can be integrated with Ansible instead to implement an end-to-end process.
  • Ansible is a great replacement for Bash scripts. It natively supports many modules that will save you so many lines of codes, enforces readable YAML structure and is still very flexible and powerful.
Terraform, Chef, Docker, Jenkins
Eric Mann | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Ansible to automate provisioning of both Amazon AMIs and other EC2 resources. It orchestrates the installation of all of the software we need to power our platform in production and leaves us with a reliable, predictable machine state on every run.

We've also used Ansible to vary the state of dependencies installed on a machine after it's been deployed to production.
  • Predictable machine state.
  • Cross-platform operation. We run Ansible from both Mac and Linux reliably.
  • There is no "official" Windows support for a host machine. Some of our team is on Windows, so this is a major drawback.
  • Some of the community-maintained packages break dependencies, requiring us to toggle a "verbose" flag in Ansible to dive into the details of what failed.
  • A recent update to Ansible itself broke on the LTS version of Ubuntu we were using. As older versions of Ansible had been purged from the package manager, we had to switch to a different installation routine entirely (using Python and pip) to restore to an active, reliable state.
Well suited: Automatic server provisioning for multiple deployment environments (development, staging, quality assurance, production, etc). It's also useful for kick-starting a new engineer's development environment so they can be productive on day 1.

Less appropriate: Rebuilding projects for integration testing. Tests are things that (should) run frequently on every build. As Ansible downloads a lot of resources over the wire (and often without a local cache), this can drastically increase the time required for an incremental build and test.
  • The time savings of not having to manually provision servers has been huge!
  • Keeping multiple servers in complete parity with one another has been incredibly helpful in reducing the number of single-machine configuration bugs present during development.
SaltStack's syntax and configuration felt a little too much like "black magic" for reliability. Several third-party packages were referenced by name only and either hid or obfuscated how they installed their dependencies (or were targeting only one distribution of Linux and failing to disclose incompatibilities with others). Ansible is far more flexible and the community package support is far superior.
Docker, Vagrant
Return to navigation